Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Nov 14, 2025

Synchronous file operations (std::fs) were blocking the async runtime in two locations within the provisioning controller.

Changes

  • provision_component: Replaced std::fs::rename with tokio::fs::rename when renaming policy files after component loading
  • verify_digest: Made function async and replaced std::fs::read with tokio::fs::read for component digest verification

Example

// Before: blocks async executor
std::fs::rename(&policy_path, &final_policy_path)?;

// After: yields to executor during I/O
tokio::fs::rename(&policy_path, &final_policy_path).await?;

Additional fixes

  • Added missing profile field to test fixture constructors in config.rs
  • Resolved clippy warnings (needless lifetimes, len_zero)

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Copilot AI changed the title [WIP] Implement headless mode policy enforcement and runtime permission handling Replace blocking file I/O with async operations in provisioning controller Nov 14, 2025
Copilot AI requested a review from Mossaka November 14, 2025 04:09
@Mossaka Mossaka closed this Nov 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants